When you log on to SAS^® Model Manager by selecting Launch using Java Web Start, the following error occurs.

 
java.lang.RuntimeException: mid-tier init() failed. 
 at com.sas.modelmanager.impl.MetadataDelegate.getMmRepository(MetadataDelegate.java:99)
 at com.sas.modelmanager.impl.MMFolderDelegate.getRoot(MMFolderDelegate.java:40)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
 at java.lang.reflect.Method.invoke(Method.java:611) 
 at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:309)
 at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
 .....
Caused by: java.lang.RuntimeException: java.lang.RuntimeException:
com.sas.analytics.modelmanager.core.AuthorizationException: 
The application could not connect to the SAS Metadata Repository 
"dav://aalsas-dev.uhc.com:443/SASContentServer/repository/default/ModelManager".
Make sure that the SAS Content Server is available, and that the user is a member of a SAS Model Manager group.
 at com.sas.analytics.modelmanager.server.RemoteModelManagementImpl.init(RemoteModelManagementImpl.java:3504)
 at com.sas.modelmanager.impl.MetadataDelegate.getMmRepository(MetadataDelegate.java:97)
  ... 145 more 

The problem occurs when the following configuration has a mixture of HTTP and HTTPS protocols.

Select SAS Management Console ► Foundation Services Manager ► SASModelmanager3.1 Local Services ► Core. Highlight Information Service. Right-click and select Properties ► Services Configuration ► Configuration ► Repositories. Select DAV ► edit. Specify HTTPS as the Proxy URL to use the secure socket layer.

In the above scenario, the configuration has a mixture of HTTP and HTTPS protocols. The problem does not occur if you use all HTTPS or all HTTP protocols.

Content returned in WebDAV responses reflects the protocol, host, and port of the origin server. However, when a reverse proxy server is used, the protocol, host, and port of the proxy server needs to be in the response. Recommended configuration options already pass the proxy host through to the origin server, so proxy is not a problem. However, if the port or protocol that is used mixes secure and non-secure in the two connections (client-proxy and proxy-server), then the problem occurs.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for this issue for SAS Model Manager 12.1 is available at:

A fix for this issue for SAS Model Manager 12.1_M1 is available at:

A fix for this issue for SAS Portal and Portlets 4.31_M1 is available at:

A fix for this issue for SAS Model Manager 3.1_M1 is available at:

A fix for this issue for SAS Model Manager 3.1 is available at:

A fix for this issue for SAS Management Console 9.3_M2 is available at:

A fix for this issue for SAS Middle Tier 9.3_M2 is available at:

A fix for this issue for SAS Middle Tier 9.3_M1 is available at: